Upgrade owned_ttf_parser to 0.13.2
+ pre-parse subtables
#48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During the update to
0.13
I noticed performance regressions withglyph_index
&kern
due to the ttf-parser refactor. However, these lead to deeper discoveries that each call was causing subtables to be parsed per-call (ultimately as ttf-parser avoids all allocation).I've now upgraded owned_ttf_parser crate with the ability to pre-parse these subtables. This PR uses that ability to provide much faster layout performance.
Bench comparisons with the current verson
Layout scenario benches are ~25-30% faster.